done somehow make the results more accurate.

done the problem is that many connection packets are blasted at the same time,
therefore the last packets collide onto the ethernet
it turns out it takes 3seconds (roughly) before the attempt to resent occurs.
so the connection packet goes out 3 seconds after nx thought it did
but now the connection attempt will probably timeout giving the wrong result
idea1: make sure there is at least 1ms between packets
ie, some packets are trying to get back, but too much traffic.

done timeouts per plugin

allow for chaining multiple plugins on the same port
make a decent scripting language per port

bugs to fix:
statistics dont work when -interval -1 is used
when a short interval is used, and all of them timeout, somehow it just ends
try this: nx -socks 50 -timeout .001 -v -interval 1 -p 1-20000 ninja

addumptions: for the iSocketToIndexMap we assume that sockets return handles <=64k

fix gethostbyname so that when net is down it loops
make plugins run off an input file rather than a scan
make heartbeat thing smarter
add syn scan (w/ decoys)
add ftp scan
add resume